-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[NONEVM-641] Starting Gauntlet Plus Plus Container on e2e test startup and Refactored tests to use GPP #554
Open
chray-zhang
wants to merge
24
commits into
develop
Choose a base branch
from
chray-zhang/gpp-container-v2
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chray-zhang
temporarily deployed
to
integration
November 25, 2024 22:17 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
November 25, 2024 22:17 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
November 25, 2024 22:17 — with
GitHub Actions
Inactive
chray-zhang
had a problem deploying
to
integration
November 25, 2024 22:30 — with
GitHub Actions
Error
chray-zhang
had a problem deploying
to
integration
November 25, 2024 22:30 — with
GitHub Actions
Failure
chray-zhang
temporarily deployed
to
integration
November 26, 2024 00:06 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
November 26, 2024 00:06 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
November 26, 2024 00:06 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
November 26, 2024 00:18 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
November 26, 2024 00:18 — with
GitHub Actions
Inactive
chray-zhang
changed the title
Initial commit with gpp container starting with permissions from local
[NONEVM-641] Starting Gauntlet Plus Plus Container on e2e test startup
Nov 26, 2024
chray-zhang
temporarily deployed
to
integration
December 2, 2024 04:00 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 2, 2024 04:00 — with
GitHub Actions
Inactive
chray-zhang
had a problem deploying
to
integration
December 2, 2024 04:00 — with
GitHub Actions
Error
chray-zhang
changed the title
[NONEVM-641] Starting Gauntlet Plus Plus Container on e2e test startup
[NONEVM-641] Starting Gauntlet Plus Plus Container on e2e test startup and Refactored tests to use GPP
Dec 2, 2024
chray-zhang
had a problem deploying
to
integration
December 2, 2024 04:10 — with
GitHub Actions
Error
chray-zhang
temporarily deployed
to
integration
December 2, 2024 04:10 — with
GitHub Actions
Inactive
chray-zhang
had a problem deploying
to
integration
December 2, 2024 04:10 — with
GitHub Actions
Error
chray-zhang
temporarily deployed
to
integration
December 2, 2024 04:16 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 2, 2024 04:16 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 2, 2024 04:16 — with
GitHub Actions
Inactive
chray-zhang
had a problem deploying
to
integration
December 2, 2024 04:29 — with
GitHub Actions
Error
chray-zhang
had a problem deploying
to
integration
December 2, 2024 04:29 — with
GitHub Actions
Error
chray-zhang
temporarily deployed
to
integration
December 2, 2024 04:31 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 2, 2024 04:31 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 2, 2024 04:31 — with
GitHub Actions
Inactive
chray-zhang
had a problem deploying
to
integration
December 2, 2024 04:43 — with
GitHub Actions
Failure
chray-zhang
temporarily deployed
to
integration
December 4, 2024 03:30 — with
GitHub Actions
Inactive
chray-zhang
had a problem deploying
to
integration
December 4, 2024 03:43 — with
GitHub Actions
Error
chray-zhang
had a problem deploying
to
integration
December 4, 2024 03:43 — with
GitHub Actions
Error
chray-zhang
temporarily deployed
to
integration
December 4, 2024 04:09 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 4, 2024 04:09 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 4, 2024 04:09 — with
GitHub Actions
Inactive
chray-zhang
had a problem deploying
to
integration
December 4, 2024 04:22 — with
GitHub Actions
Error
chray-zhang
had a problem deploying
to
integration
December 4, 2024 04:22 — with
GitHub Actions
Failure
chray-zhang
temporarily deployed
to
integration
December 4, 2024 14:44 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 4, 2024 14:44 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 4, 2024 14:44 — with
GitHub Actions
Inactive
chray-zhang
had a problem deploying
to
integration
December 4, 2024 14:58 — with
GitHub Actions
Error
chray-zhang
had a problem deploying
to
integration
December 4, 2024 14:58 — with
GitHub Actions
Failure
chray-zhang
had a problem deploying
to
integration
December 4, 2024 20:47 — with
GitHub Actions
Failure
chray-zhang
had a problem deploying
to
integration
December 4, 2024 20:47 — with
GitHub Actions
Error
chray-zhang
temporarily deployed
to
integration
December 4, 2024 21:31 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 4, 2024 21:31 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 4, 2024 21:31 — with
GitHub Actions
Inactive
chray-zhang
had a problem deploying
to
integration
December 4, 2024 21:47 — with
GitHub Actions
Error
chray-zhang
had a problem deploying
to
integration
December 4, 2024 21:47 — with
GitHub Actions
Failure
chray-zhang
temporarily deployed
to
integration
December 6, 2024 05:19 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 6, 2024 05:19 — with
GitHub Actions
Inactive
chray-zhang
temporarily deployed
to
integration
December 6, 2024 05:19 — with
GitHub Actions
Inactive
chray-zhang
had a problem deploying
to
integration
December 6, 2024 05:31 — with
GitHub Actions
Failure
chray-zhang
had a problem deploying
to
integration
December 6, 2024 05:31 — with
GitHub Actions
Error
Quality Gate passedIssues Measures |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
core ref: baf88355a2d349a621ce88db20fbfdd1617f4559
Description
As part of the effort to migrate the E2E tests from legacy gauntlet to gauntlet++ we need to start an instance of Gpp on E2E test initialization. This ticket starts a Gpp container on start up.
Tickets
https://smartcontract-it.atlassian.net/browse/NONEVM-330
HOW TO Run
Make sure you have the
gauntlet-plus-plus:v2.5.0
image from the prod ECR in dockersource test.env
cd integration-tests/smoke
go test -v
If you get this error:
Just re run the tests with
go test -v
. The above is usually a race condition with declaring the contract or something